docs: align release workflow with PR-only rule; bump release action to Node 24#23
Merged
Conversation
Remote master enforces "changes must go through a pull request" (GH013), so version bumps can't be pushed directly to master as the old instructions claimed. Rewrite the version-bump section: bump via its own standalone PR, then push the vX.Y.Z tag separately after merge (tags aren't covered by the branch rule). Also note that release.yml publishes to crates.io, not just GitHub Releases. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
softprops/action-gh-release@v2 runs on the deprecated Node 20 runtime; v3.0.0 moves to Node 24 with no input/behavior changes. The other actions (checkout@v6, upload-artifact@v7, download-artifact@v8, rust-cache@v2) are already on their latest major and Node 24. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
rrbe
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Two release-workflow housekeeping changes, bundled per request.
Docs: version-bump flow matches branch protection
CLAUDE.md claimed version bumps were an allowed direct-to-
masterexception, but remotemasterenforces "changes must go through a pull request" (git push origin master→GH013). Surfaced while cutting v0.6.1. Rewrote the version-bump section:vX.Y.Ztag is pushed separately after the bump PR merges — tags aren't covered by the branch rule, so that push succeeds directly.release.ymlalso publishes to crates.io (cargo publish), not just GitHub Releases.Chore: bump release action off deprecated Node 20
softprops/action-gh-release@v2runs on the deprecated Node 20 runtime. v3.0.0 is a runtime-only move to Node 24 (no input/behavior changes), so@v2→@v3. Audited the rest —checkout@v6,upload-artifact@v7,download-artifact@v8,rust-cache@v2are all already on their latest major and Node 24, so no other bumps needed.🤖 Generated with Claude Code